Gravity Forms v1.6 Beta 2 is now available. This is a bug fix release and we highly recommend users of Beta 1 upgrade now to Beta 2. We look forward to continue receiving feedback from users who want to help test out the new features.
Please provide beta feedback and bug reports on the Support Forum and make it clear you are referring to the 1.6 Beta 2 release when doing so. Thanks!
What's New
- Added browser class to gform_wrapper.
- Fixed problem with unchecking "enable enhanced user interface" setting.
- Added a form specific class to the confirmation container. "gform_confirmation_message_FORMID".
- Fixed issue where adding any post field to a form prevented the form from saving if Post Formats were not supported.
- Fixed problem creating warning messages on radio button fields.
- Fixed issue with entry count on the form list page and dashboard widget taking entries in the trash and spam folder into account.
- Added extra classes to pagination steps.
- Fixed issue on entry list causing the bulk action "apply" button to fire when pressing then enter on the search input.
We will be releasing v1.6 via automatic upgrade once it has undergone beta testing. Own Gravity Forms and want to give it a try and help us test? Grab a copy on the downloads page!
Don't own Gravity Forms yet? What are you waiting for?! Purchase a copy today!
Share This
Thanks to the whole Gravity team for this awesome new version! I tested beta 1 and now beta 2 and so far all is working very well - I had the issue with the post format not saving and glad it's fixed now! (Thought it was my fault...)
However, as I am doing all the German translations for Gravity Forms I found out some areas not yet localized. To understand me better, I posted some screenshots - and will give some explantion to them. All areas are with numbers so I hope you get what I mean.
Here it goes:
(1) Single Entry View - screen: http://ow.ly/i/gBid/original
1 = "Form Settings" - we need a lot more space for this word to translate! The proper German word would be "Formular-Einstellungen" which is way too wide for the column width as of now... So please add a bit more width as it seems we have a lot for that... (What you see on the screen is the current German translation which is only a "construct" but not really useable at this point)
This issue is always where this bar is displayed!
2 + 3 = not yet localized - or maybe localized strings are not catched?
4 = Localizing works - but we need more space again for the button text. In this case the correct German word would be "Notiz hinzufügen" which is a bit longer but cut off as of now...
(2) Single Entry Print Preview - screen: http://ow.ly/i/gBij/original
1 = not yet localized - or maybe localized strings are not catched?
2 = We need more space for this again (was in English "close window") - so have that space just widen the column width...
(3) Gravity Dashboard Widget - screen: http://ow.ly/i/gBix/original
Currently all strings are not yet localized - or maybe localized strings are not catched?
Thank you, Dave 🙂
Thanks Dave! We'll be in touch regarding the localization issues you pointed out.
Loving the new updates in 1.6 - another excellent job. Found a possible bug on ajax multipage forms which I've added to the forum. Looking forward to the stable version!
Thank you, Carl!
I have the formal translation ready for 1.6 beta 2 - and now working on the informal version will post both on the forum for users to test. I hope in the next 1 or 2 days... I hope that this just in time with release...
Greetinx, dave 🙂
I have updated the German language files for 1.6 Beta 2 - for formal and informal version.
In this forum post are the downloads for both files and a call to all users of the German language packs to test them:
http://www.gravityhelp.com/forums/topic/beta-test-german-lang-files-for-16-beta2-deutsche-sprachdateien-fuer-16-bet
I hope this helps 🙂
@Carl & Team:
You use them as well 🙂
I will update any new strings if there are new betas, RC's or such!
Servus, Dave 🙂
Thanks! We'll be sure to include it in the next release. I don't believe there will be any additional strings added as it's typically feature related when we do.
I'm a big fan of the improvements in the 1.6 beta. Masks are fun, duplicating fields make my life easier and on and on. For one of the new functions though, the user_logged_in check, I wish that it went both ways -- meaning the choice to show or not to show if a user is logged in.
Example: I have a multi-page submission form where the first page is a registration form (with required fields). I'd like to be able to HIDE a form to logged-in users.
I've been using a little switch redirect that checks for this, but a built-in function would be cool too. Any hope for inclusion in a later iteration?
Of course, now I see the ability to add shortcodes to the not-logged-in message. Please disregard my previous comment. 🙂
@MetVisualMedia Glad you figured it out. Because the message for the require user is logged in option allows shortcode usage we felt this was sufficient because you can use this to display a form for a user that is not logged in. In the future we would like to add field level options to show/hide fields based on the user being logged in or not. We'd like to enable using a single form for both logged in and non-logged in users for different actions such as Post Creation, etc.